| 2 | Approval of Agenda | |
|---|---|---|
| R1-2200000 | Draft Agenda of RAN1#107b-e meeting | RAN1 Chair |
| R1-2200003 | RAN1#107b-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2200004 | Additional Guidelines for RAN1#107b-e-Meeting Management | RAN1 Chair |
| 3 | Highlights from RAN plenary | |
| R1-2200001 | Highlights from RAN#94-e | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2200002 | Report of RAN1#107-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2200005 | LS on paging subgrouping and PEI | RAN2, Xiaomi |
| R1-2200006 | Reply LS on time gap information in SCI | RAN2, OPPO |
| R1-2200007 | Reply LS on SL resource selection with DRX | RAN2, Lenovo |
| R1-2200008 | LS response on PC5 DRX for ProSe | RAN2, vivo |
| R1-2200009 | LS on MBS broadcast reception on SCell and non-serving cell | RAN2, Huawei |
| R1-2200010 | LS on further agreements on RLM and BFD relaxation for UE Power Saving enhancements | RAN4, vivo, MediaTek |
| R1-2200011 | Reply LS on TA-based propagation delay compensation | RAN4, Nokia |
| R1-2200072 | Discussion on MBS broadcast reception on SCell and non-serving cell | vivo |
| R1-2200073 | Draft reply LS on MBS broadcast reception on SCell and non-serving cell | vivo |
| R1-2200106 | [Draft] Reply LS on MBS broadcast reception on SCell and non-serving cell | ZTE |
| R1-2200127 | Discussion on Reply LS on SL Resource Selection with DRX | CATT, GOHIGH |
| R1-2200128 | [Draft] Reply LS on P_EMAX for NR-V2X | CATT, GOHIGH |
| R1-2200129 | Discussion on Reply LS on MBS broadcast reception on SCell and non-serving cell | CATT |
| R1-2200272 | Discussion on MBS broadcast reception on SCell and non-serving cell | Spreadtrum Communications |
| R1-2200289 | Draft Reply LS to RAN4 on PEMAX for NR-V2X | Qualcomm Incorporated |
| R1-2200353 | Discussion on broadcast reception on Scell and non-serving cell in LS from RAN2 | OPPO |
| R1-2200448 | Draft reply on MBS broadcast reception on SCell and non-serving cell | xiaomi |
| R1-2200547 | Discussion on RAN2 LS on MBS broadcast reception on SCell and non-serving cell | MediaTek Inc. |
| R1-2200548 | Reply LS on MBS broadcast reception on SCell and non-serving cell | MediaTek Inc. |
| R1-2200561 | Discussion on Reply LS on UE capability for supporting single DCI transmission schemes for multi-TRP | Ericsson |
| R1-2200584 | Discussion on LS on MBS broadcast reception on SCell and non-serving cell | CMCC |
| R1-2200639 | [Draft] Reply LS on SL resource selection with DRX | Ericsson |
| R1-2200640 | Discussion on RAN2 LS on SL resource selection with DRX | Ericsson |
| R1-2200645 | About reply LS on SL resource selection with DRX | ZTE, Sanechips |
| R1-2200647 | Discussion on MBS broadcast reception on SCell and non-serving cell | Huawei, HiSilicon, CBN |
| R1-2200648 | DRAFT LS reply to MBS broadcast reception on SCell and non-serving cell | Huawei, HiSilicon |
| R1-2200716 | Incoming LS handling for RAN1#107bis-e | RAN1 Chair |
| 8 | Release 17 | |
| R1-2200698 | DRAFT LS on updated Rel-17 NR higher-layers parameter list | Moderator (Ericsson) |
| R1-2200699 | Consolidated higher layers parameter list for Rel-17 NR | Moderator (Ericsson) |
| R1-2200700 | LS on updated Rel-17 NR higher-layers parameter list | RAN1, Ericsson |
| R1-2200701 | Summary of Email discussion on Rel-17 RRC parameters for LS to RAN2 | Moderator (Ericsson) |
| R1-2200702 | Collection of updated higher layers parameter list for Rel-17 NR | Moderator (Ericsson) |
| 8.2 | Maintenance on Supporting NR from 52.6GHz to 71 GHz | |
| R1-2200792 | Session notes for 8.2 (Extending current NR operation to 71GHz) | Ad-Hoc Chair (Huawei) |
| R1-2200804 | FL summary for RRC parameter discussion for 52.6 to 71GHz band | Moderator (Qualcomm) |
| R1-2200805 | Session notes for 8.2 (Extending current NR operation to 71GHz) | Ad-Hoc Chair (Huawei) |
| R1-2200808 | List of agreements of Rel-17 52.6-71GHz WI (post RAN1#107bis-e) | Moderator (Qualcomm) |
| R1-2200812 | Corrections further to the introduction for extending NR operation to 71 GHz | Samsung |
| R1-2200818 | Corrections to NR in the 52.6 – 71 GHz range | Ericsson |
| R1-2200820 | Corrections of the features extending NR operation to 71 GHz | Ericsson |
| R1-2200824 | Corrections further to the introduction for extending NR operation to 71 GHz | Nokia |
| 8.2.1 | Initial access aspects | |
| R1-2200024 | On remaining issues for initial access for Beyond 52.6GHz | FUTUREWEI |
| R1-2200044 | Remaining issue of initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200059 | Remaining issues for initial access operation in 52.6-71GHz | InterDigital, Inc. |
| R1-2200074 | Remaining issues on initial access aspects for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2200142 | Remaining issues on Initial access aspects for up to 71GHz operation | CATT |
| R1-2200183 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2200192 | Maintenance on initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2200226 | Remaining issues on initial access aspects for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2200259 | Remaining issues on the initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2200273 | Discussion on initial access aspects for NR for 60GHz | Spreadtrum Communications |
| R1-2200324 | Discussion on remaining issue for initial access aspects | OPPO |
| R1-2200355 | Remaining issues on initial access aspects for NR from 52.6 to 71GHz | ETRI |
| R1-2200366 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2200400 | Initial Access Aspects | Ericsson |
| R1-2200409 | On remaining issues for initial access | Apple |
| R1-2200494 | Initial access aspects | Sharp |
| R1-2200564 | Initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2200688 | Issue Summary for initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2200689 | Summary #1 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2200690 | Summary #2 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| 8.2.2 | PDCCH monitoring enhancements | |
| R1-2200045 | Remaining issues of PDCCH monitoring enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200060 | Remaining issues for PDCCH monitoring enhancements | InterDigital, Inc. |
| R1-2200075 | Remaining issues on PDCCH monitoring enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2200143 | Remaining issues on PDCCH monitoring enhancements for up to 71GHz operation | CATT |
| R1-2200174 | PDCCH enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2200184 | PDCCH monitoring enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200193 | Maintenance on PDCCH monitoring enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2200227 | Remaining issues on PDCCH monitoring enhancements for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2200260 | Remaining issues on the PDCCH monitoring enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2200290 | PDCCH monitoring enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2200325 | Discussion on remaining issue for PDCCH monitoring enhancement | OPPO |
| R1-2200367 | Discussion on PDCCH monitoring enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2200401 | PDCCH Monitoring Enhancements | Ericsson |
| R1-2200410 | On remaining issues for PDCCH Monitoring | Apple |
| R1-2200459 | Remaining issues on PDCCH monitoring enhancement for NR 52.6-71GHz | xiaomi |
| R1-2200495 | PDCCH monitoring enhancements | Sharp |
| R1-2200507 | Remaining issues on PDCCH enhancement for NR operation from 52.6GHz to 71GHz | NEC |
| R1-2200540 | Remaining discussion on PDCCH monitoring enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2200558 | Remaining issues of PDCCH monitoring enhancements for above 52.6GHz | Transsion Holdings |
| R1-2200565 | PDCCH monitoring enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2200654 | PDCCH monitoring for NR operation from 52.6 to 71 GHz | Panasonic |
| R1-2200671 | Remaining issues on PDCCH for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2200709 | Feature lead summary #1 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2200710 | Feature lead summary #2 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2200711 | Feature lead summary #3 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| 8.2.3 | Enhancements for PUCCH formats 0/1/4 | |
| R1-2200046 | Remaining issues of PUCCH enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200061 | Remaining issues for enhanced PUCCH formats 0/1/4 | InterDigital, Inc. |
| R1-2200076 | Remaining issues on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2200175 | Remaining issues on enhancements for PUCCH formats 0/1/4 | Sony |
| R1-2200185 | Finalization of enhanced PUCCH formats 0/1/4 | Nokia, Nokia Shanghai Bell |
| R1-2200194 | Maintenance on enhancements for PUCCH format 0/1/4 for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2200228 | Remaining issues on PUCCH format 0/1/4 enhancements for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2200261 | Remaining issues on the PUCCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2200326 | Discussion on remaining issue for enhancements for PUCCH format 0/1/4 | OPPO |
| R1-2200368 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2200402 | PUCCH enhancements | Ericsson |
| R1-2200403 | FL Summary for Enhancements for PUCCH formats 0/1/4 | Ericsson |
| R1-2200446 | Remaining issues on PUCCH formats enhancements for beyond 52.6GHz | FUTUREWEI |
| R1-2200566 | Enhancements for PUCCH formats 0/1/4 to support NR above 52.6 GHz | LG Electronics |
| R1-2200679 | Remaining issues on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| 8.2.4 | Beam management for new SCSs | |
| R1-2200047 | Remaining issues of beam management enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200062 | Remaining issues for beam management for new SCSs | InterDigital, Inc. |
| R1-2200063 | Discussion Summary #1 for Beam Management for new SCSs | Moderator (InterDigital, Inc.) |
| R1-2200077 | Remaining issues on beam management for new SCSs for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2200144 | Remaining issues on beam management for new SCSs for up to 71GHz operation | CATT |
| R1-2200176 | Remaining issues on beam management enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2200186 | Beam Management Aspects | Nokia, Nokia Shanghai Bell |
| R1-2200195 | Maintenance on beam management for new SCSs for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2200229 | Remaining issues on Beam based operation for new SCSs for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2200262 | Remaining issues on the beam management for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2200291 | Beam management for new SCS | Qualcomm Incorporated |
| R1-2200327 | Discussion on remaining issue for beam management for new SCSs | OPPO |
| R1-2200369 | Discussion on Beam management aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2200404 | Beam Management for New SCSs | Ericsson |
| R1-2200411 | Beam Management for New SCSs | Apple |
| R1-2200447 | On issues in Beam Management for Beyond 52.6 GHz | FUTUREWEI |
| R1-2200460 | Maintenance on beam management for new SCSs | xiaomi |
| R1-2200515 | Beam management enhancement for NR from 52.6GHz to 71GHz | NEC |
| R1-2200541 | Remaining discussion on beam management for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2200567 | Enhancements for beam management to support NR above 52.6 GHz | LG Electronics |
| R1-2200672 | Remaining issues on beam-management for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2200760 | Discussion Summary #2 of Beam Management for New SCSs | Moderator (InterDigital) |
| R1-2200761 | Discussion Summary #3 of Beam Management for New SCSs | Moderator (InterDigital) |
| R1-2200783 | [Draft] LS on a minimum guard period between two SRS resources for antenna switching | InterDigital |
| R1-2200796 | LS on a minimum guard period between two SRS resources for antenna switching | RAN1, InterDigital |
| 8.2.5 | PDSCH/PUSCH enhancements | |
| R1-2200025 | On several study points for PDSCH/PUSCH enhancements for Beyond 52.6GHz | FUTUREWEI |
| R1-2200048 | Remaining issues of PDSCH/PUSCH enhancement for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2200064 | Remaining issues for PDSCH/PUSCH enhancements to supporting 52.6-71 GHz band in NR | InterDigital, Inc. |
| R1-2200078 | Remaining issues on PDSCH/PUSCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2200124 | Remaining issues of multi-PDSCH scheduling via a single DCI | Fujitsu |
| R1-2200145 | Remaining issues on PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2200187 | PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200196 | Maintenance on PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2200230 | Remaining issues on PDSCH/PUSCH enhancements for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2200263 | Remaining issues on the data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2200267 | Discussion on PDSCH/PUSCH enhancements for NR 52.6-71 GHz | Panasonic Corporation |
| R1-2200292 | PDSCH/PUSCH enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2200328 | Discussion on remaining issue for PDSCH/PUSCH enhancements | OPPO |
| R1-2200370 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2200405 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2200412 | On remaining issues for PDSCH/PUSCH Enhancements | Apple |
| R1-2200461 | Remaining issues on PDSCH and PUSCH enhancements for NR 52.6-71GHz | xiaomi |
| R1-2200508 | Remaining issues on PDSCH/PUSCH enhancement for NR operation from 52.6GHz to 71GHz | NEC |
| R1-2200542 | Remaining discussion on multi-PDSCH scheduling design for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2200568 | PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2200569 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2200631 | Discussion on multi-PUSCH scheduling | ASUSTeK |
| R1-2200632 | Remaining issues on PDSCH/PUSCH enhancement for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2200684 | Discussion summary #1 of [107bis-e-R17-52-71GHz-05] | Moderator (vivo) |
| R1-2200744 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| 8.2.6 | Channel access mechanism | |
| R1-2200026 | On Issues in Channel Access for Beyond 52.6 GHz | FUTUREWEI |
| R1-2200049 | Remaining issues of channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2200065 | Remaining issues for channel access mechanisms | InterDigital, Inc. |
| R1-2200079 | Remaining issues on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2200146 | Remaining issues on channel access mechanism for up to 71GHz operation | CATT |
| R1-2200177 | Remaining issues on channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2200188 | Remaining issues on Channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2200197 | Maintenance on channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2200231 | Remaining issues on Channel access mechanism for NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2200264 | Remaining issues on the channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2200293 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2200329 | Discussion on remaining issue for channel access mechanism | OPPO |
| R1-2200371 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2200406 | Channel Access Mechanisms | Ericsson |
| R1-2200413 | Remaining issues on channel access mechanisms | Apple |
| R1-2200462 | Remaining issues on channel access mechanism for NR on 52.6-71 GHz | xiaomi |
| R1-2200514 | Remaining issues on channel access mechanism supporting NR from 52.6 to 71 GHz | NEC |
| R1-2200539 | On the channel access mechanisms for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2200559 | Remaining issues of channel access mechanism for above 52.6GHz | Transsion Holdings |
| R1-2200570 | Channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2200621 | Remaining issue on channel access scheme for above 52.6GHz | ASUSTeK |
| R1-2200633 | Remaining issue on channel access for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2200662 | Discussion on sharing of directional channel occupancy | Panasonic |
| R1-2200673 | Remaining issues on channel access for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2200703 | FL summary#1 for channel access for 52.6 to 71 GHz band | Moderator (Qualcomm) |
| R1-2200753 | FL summary#2 for channel access for 52.6 to 71 GHz band | Moderator (Qualcomm) |
| R1-2200803 | FL summary#3 for channel access for 52.6 to 71 GHz band | Moderator (Qualcomm) |
| 8.2.7 | Other | |
| R1-2200265 | Discussion on RRC parameters for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2200407 | SSB-CORESET0 offsets for the 57 – 71 GHz band | Ericsson |
| R1-2200652 | Discussion on the channel raster and sync raster in FR2-2 | Huawei, HiSilicon |
| 8.3 | Enhanced Industrial Internet of Things (IoT) and URLLC | |
| R1-2200777 | Summary of [107bis-e-R17-RRC-IIoT-URLLC] Email discussion on Rel-17 RRC parameters for IIoT and URLLC | Moderator (Nokia) |
| R1-2200778 | List of agreements of Rel-17 URLLC/IIoT WI (post RAN1#107bis-e) | WI rapporteur (Nokia) |
| R1-2200813 | Corrections further to the introduction of IIoT/URLLC enhancements in NR | Samsung |
| R1-2200821 | Corrections of the semi-static channel access mode with UE initiating channel occupancy for IIoT/URLLC enhancements in NR | Ericsson |
| R1-2200825 | Corrections further to the introduction of IIoT/URLLC enhancements in NR | Nokia |
| R1-2200829 | Corrections on enhanced IIoT and URLLC in 38.212 | Huawei |
| 8.3.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2200017 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2200020 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2200037 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2200080 | Remaining issues on HARQ-ACK enhancements for Rel-17 URLLC | vivo |
| R1-2200107 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2200147 | Remaining issues on HARQ-ACK feedback enhancements | CATT |
| R1-2200178 | Remaining issues in HARQ-ACK enhancements for URLLC | Sony |
| R1-2200198 | Remaining issues for HARQ-ACK feedback enhancements | Samsung |
| R1-2200232 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2200269 | UE feedback enhancements for HARQ-ACK | CAICT |
| R1-2200274 | Discussion on HARQ-ACK feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2200294 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2200319 | Discussion on one-shot triggering of HARQ retransmission | Panasonic Corporation |
| R1-2200343 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2200356 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2200372 | Remaining issues on UE HARQ feedback enhancements | Intel Corporation |
| R1-2200395 | Remaining issues on HARQ enhancements for URLLC | InterDigital, Inc. |
| R1-2200414 | Rel-17 UE feedback enhancements for HARQ-ACK | Apple |
| R1-2200440 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2200484 | Discussion on some remaining issues for UE HARQ-ACK feedback enhancements | China Telecom |
| R1-2200516 | UE feedback enhancements for HARQ-ACK | NEC |
| R1-2200530 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2200556 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2200571 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2200729 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2200730 | Moderator summary #3 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2200775 | Moderator summary #4 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2200776 | Final moderator summary on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| 8.3.2 | Enhancements for unlicensed band URLLC/IIoT | |
| R1-2200038 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, HiSilicon |
| R1-2200081 | Remaining issues on enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2200108 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2200166 | Enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2200179 | Remaining issues in unlicensed URLLC | Sony |
| R1-2200295 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2200357 | Remaining issues on unlicensed band URLLC/IIoT | ETRI |
| R1-2200373 | Remaining Clarifications for Enabling URLLC/IIoT in Unlicensed Band | Intel Corporation |
| R1-2200396 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2200415 | Remaining issues on URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2200441 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2200496 | Enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2200572 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2200634 | Remaining issues on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2200691 | Summary#1 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2200692 | Summary#2 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2200693 | Summary#3 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2200694 | Summary#4 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2200695 | Summary#5 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| 8.3.3 | Intra-UE Multiplexing/Prioritization | |
| R1-2200012 | Intra-UE multiplexing and prioritization | New H3C Technologies Co., Ltd. |
| R1-2200018 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200039 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2200082 | Remaining issues on intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2200109 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2200148 | Remaining issues on intra-UE multiplexing and prioritization | CATT |
| R1-2200180 | Remaining issues in intra-UE multiplexing & prioritisation | Sony |
| R1-2200199 | Remaining issues for Intra-UE Multiplexing/Prioritization | Samsung |
| R1-2200233 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2200275 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2200296 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2200320 | Discussion on intra-UE multiplexing with different priorities | Panasonic Corporation |
| R1-2200344 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2200358 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2200365 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2200374 | Remaining Open Details of Intra-UE Uplink Channel Multiplexing and Prioritization | Intel Corporation |
| R1-2200416 | Rel-17 intra-UE Multiplexing/Prioritization | Apple |
| R1-2200442 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2200485 | Discussion on some remaining issues for intra-UE multiplexing and prioritization | China Telecom |
| R1-2200492 | Remaining Issues on Intra-UE Multiplexing/Prioritization | Quectel, Langbo |
| R1-2200497 | Intra-UE UCI multiplexing and channel collision resolution with different priorities | Sharp |
| R1-2200517 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2200531 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2200562 | Discussion on intra-UE multiplexing and prioritization | ITRI |
| R1-2200573 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2200635 | Remainng issues on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2200704 | Summary #1 of email thread [107bis-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2200715 | Summary#1 of email thread [107bis-e-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2200725 | Summary #2 of email thread [107bis-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2200728 | Summary#2 of email thread [107bis-e-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2200737 | Summary #3 of email thread [107bis-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2200738 | Summary #4 of email thread [107bis-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2200739 | Summary #5 of email thread [107bis-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2200757 | Summary#3 of email thread [107bis-e-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2200770 | Rel-17 intra-UE Multiplexing/Prioritization | Apple |
| R1-2200771 | Summary #6 of email thread [107bis-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2200772 | Summary #7 of email thread [107bis-e-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2200791 | Summary#4 of email thread [107bis-e-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| 8.3.4 | Other | |
| R1-2200013 | Discussion on propagation delay compensation enhancements | New H3C Technologies Co., Ltd. |
| R1-2200019 | On remaining issues of propagation delay compensation | Nokia, Nokia Shanghai Bell |
| R1-2200110 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2200200 | Remaining issues for propagation delay compensation enhancements | Samsung |
| R1-2200297 | Remaining issues for CSI enhancement for IIOT and URLLC | Qualcomm Incorporated |
| R1-2200345 | Enhancement for support of time synchronization | OPPO |
| R1-2200375 | Remaining issues for RTT-based propagation delay compensation | Intel Corporation |
| R1-2200443 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2200574 | Discussion on propagation delay compensation enhancements | LG Electronics |
| R1-2200650 | Enhancements for support of time synchronization | Huawei, HiSilicon |
| R1-2200677 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2200755 | Summary #1 of [107bis-e-R17-IIoT-URLLC-06] Email discussion on CSI feedback enhancements | Moderator (InterDigital) |
| R1-2200756 | Feature lead summary#1 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2200799 | Final feature lead summary on propagation delay compensation enhancements | Moderator (Huawei) |
| 8.4 | VOID (Solutions for NR to support non-terrestrial networks (NTN)) | |
| R1-2200674 | MEO Scenarios and Characteristics | HUGHES Network Systems Ltd |
| 8.7 | Maintenance on UE Power Saving Enhancements | |
| R1-2200793 | Session notes for 8.7 (UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2200809 | Session notes for 8.7 (UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2200816 | Corrections further to the introduction of UE power savings enhancements in NR | Samsung |
| R1-2200817 | Collection of RAN1-related agreements for UE power saving enhancements for NR | Rapporteur (MediaTek) |
| R1-2200828 | Corrections further to the introduction of UE power savings enhancements in NR | Nokia |
| R1-2200833 | Corrections on UE power saving enhancements in 38.212 | Huawei |
| R1-2200834 | Summary of email discussion on Rel-17 RRC parameters for UE power saving | Moderator (MediaTek Inc.) |
| 8.7.1.1 | Potential paging enhancements | |
| R1-2200032 | Remaining issues on Paging enhancements for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2200066 | Remaining issues of power saving enhancements for paging | ZTE, Sanechips |
| R1-2200083 | Remaining issues on paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2200149 | Paging enhancement for UE power saving | CATT |
| R1-2200155 | Remaining issues on paging enhancements for idle/inactive mode UE power saving | TCL Communication Ltd. |
| R1-2200201 | Maintenance on paging enhancements | Samsung |
| R1-2200234 | Discussion on paging enhancement | NTT DOCOMO, INC. |
| R1-2200276 | Discussion on potential paging enhancements for UE power saving | Spreadtrum Communications |
| R1-2200298 | Paging enhancements for idle and inactive UE power saving | Qualcomm Incorporated |
| R1-2200331 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2200362 | Open items on paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2200376 | Discussion on the remaining aspects of paging enhancements | Intel Corporation |
| R1-2200397 | On paging enhancement | Panasonic |
| R1-2200417 | Remaining issues on paging enhancements for idle/inactive UEs | Apple |
| R1-2200463 | Remaining issues on paging enhancement for power saving | xiaomi |
| R1-2200478 | Remaining aspects of Paging Enhancements | Ericsson |
| R1-2200532 | Paging enhancement for UE power saving | Lenovo, Motorola Mobility |
| R1-2200560 | Discussion on PEI Design | Transsion Holdings |
| R1-2200575 | Discussion on potential paging enhancements | LG Electronics |
| R1-2200585 | Remaining issues on paging early indication | CMCC |
| R1-2200605 | Summary#1 for Maintenance of Paging Enhancements | Moderator (MediaTek Inc.) |
| R1-2200606 | Maintenance on Design of Paging Early Indication | MediaTek Inc. |
| R1-2200609 | On paging early indication | Nordic Semiconductor ASA |
| R1-2200618 | Remaining issues on paging enhancements | InterDigital, Inc. |
| R1-2200743 | Summary#2 for Maintenance of Paging Enhancements | Moderator (MediaTek Inc.) |
| R1-2200759 | Summary#3 for Maintenance of Paging Enhancements | Moderator (MediaTek Inc.) |
| R1-2200787 | Summary#4 of Maintenance on Paging Enhancement | Moderator (MediaTek Inc.) |
| R1-2200788 | [Draft] LS on Paging Enhancement | MediaTek Inc. |
| R1-2200800 | LS on Paging Enhancement | RAN1, MediaTek Inc. |
| R1-2200801 | Summary#5 of Maintenance on Paging Enhancement | Moderator (MediaTek Inc.) |
| 8.7.1.2 | TRS/CSI-RS occasion(s) for idle/inactive UEs | |
| R1-2200033 | Remaining issue on assistance TRS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2200067 | Remaining issues of TRS for RRC idle and inactive UEs | ZTE, Sanechips |
| R1-2200084 | Remaining issues on TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2200150 | Remaining issues of TRS/CSI-RS for paging enhancement | CATT |
| R1-2200156 | Remaining issues of TRS/CSI-RS occasion(s) for idle/inactive UEs | TCL Communication Ltd. |
| R1-2200202 | Maintenance on TRS/CSI-RS occasion(s) for idle/inactive UEs | Samsung |
| R1-2200203 | Moderator Summary#1 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2200235 | Discussion on TRS/CSI-RS occasion for idle/inactive UEs | NTT DOCOMO, INC. |
| R1-2200277 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2200299 | TRS and CSI-RS for idle and inactive UE power saving | Qualcomm Incorporated |
| R1-2200332 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2200363 | Open issues on n TRS information for IDLE/INACTIVE mode UEs | Nokia, Nokia Shanghai Bell |
| R1-2200377 | Discussion on the remaining details of TRS/CSI-RS occasions in idle/inactive time | Intel Corporation |
| R1-2200398 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs | Panasonic |
| R1-2200418 | Remaining issues on indication of TRS configurations for idle/inactive UEs | Apple |
| R1-2200464 | Remaining issues on TRS/CSI-RS configuration and indication for idle/inactive UEs | xiaomi |
| R1-2200479 | Remaining aspects of TRS occasion provisioning for Idle/Inactive UEs | Ericsson |
| R1-2200498 | Remaining issues on TRS/CSI-RS occasions for idle/inactive UEs | Sharp |
| R1-2200533 | Provision of TRS/CSI-RS for idle/inactive UEs | Lenovo, Motorola Mobility |
| R1-2200576 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2200586 | Remaining issues on TRS/CSI-RS occasion(s) for idle/inactive UEs | CMCC |
| R1-2200607 | Maintenance on Design of TRS/CSI-RS Information for idle/inactive UEs | MediaTek Inc. |
| R1-2200610 | On TRS design for idle/inactive UEs | Nordic Semiconductor ASA |
| R1-2200619 | Remaining issues on TRS/CSI-RS occasions for idle/inactive UEs | InterDigital, Inc. |
| R1-2200726 | Moderator Summary#3 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2200727 | Moderator Summary#2 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2200782 | Moderator Summary #3 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| 8.7.1.3 | Other | |
| R1-2200068 | Simulation results of UE power saving in RRC idle and inactive state | ZTE, Sanechips |
| R1-2200480 | Modeling of NR gNB power consumption | Ericsson |
| R1-2200649 | Analysis on power consumption for IDLE mode UE | Huawei, HiSilicon |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | |
| R1-2200034 | Remaining issues on the extensions to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2200069 | Remaining issues of PDCCH monitoring adaptation during DRX Active Time | ZTE, Sanechips |
| R1-2200085 | Remaining issues on DCI-based power saving adaptation in connected mode | vivo |
| R1-2200151 | PDCCH monitoring adaptation | CATT |
| R1-2200167 | Discussion on DCI-based power saving adaptation | NEC |
| R1-2200204 | Maintenance on DCI-based power saving techniques | Samsung |
| R1-2200236 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2200278 | Discussion on power saving techniques for connected-mode UEs | Spreadtrum Communications |
| R1-2200300 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2200333 | DCI-based power saving adaptation solutions | OPPO |
| R1-2200364 | Open issues on PDCCH monitoring adaptation for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2200378 | Discussion on remaining aspects of power saving in active time | Intel Corporation |
| R1-2200399 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Panasonic |
| R1-2200419 | Remaining issues on enhanced DCI-based power saving adaptation | Apple |
| R1-2200465 | Remaining issues on PDCCH monitoring adaptation for power saving | xiaomi |
| R1-2200481 | Remaining aspects of active time power savings mechanisms | Ericsson |
| R1-2200534 | Enhanced DCI based power saving adaptation | Lenovo, Motorola Mobility |
| R1-2200577 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2200587 | Remaining issues on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2200608 | Maintenance on Enhancement of DCI-based PDCCH Monitoring Adaptation | MediaTek Inc. |
| R1-2200611 | On PDCCH monitoring adaptation | Nordic Semiconductor ASA |
| R1-2200620 | Remaining issues on DCI-based power saving adaptation | InterDigital, Inc. |
| R1-2200696 | FL summary#1 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2200697 | FL summary#2 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2200758 | FL summary#3 of DCI-based power saving adaptation | Moderator (vivo) |
| 8.7.3 | Other | |
| R1-2200070 | Further discussion on power saving for RRC connected UEs | ZTE, Sanechips |
| R1-2200482 | Evaluation results for UE power saving schemes | Ericsson |
| R1-2200537 | On the evaluation methodology of NR network power consumption | MediaTek Inc. |
| 8.8 | NR coverage enhancement | |
| R1-2200794 | Session notes for 8.8 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
| R1-2200811 | Corrections further to the introduction of coverage enhancements in NR | Samsung |
| R1-2200823 | Corrections further to the introduction of coverage enhancements in NR | Nokia |
| R1-2200831 | Corrections on coverage enhancements in 38.212 | Huawei |
| 8.8.1.1 | Enhancements on PUSCH repetition type A | |
| R1-2200051 | Discussion on coverage enhancements for PUSCH repetition type A | Huawei, HiSilicon |
| R1-2200086 | Remaining issues on enhancement for PUSCH repetition type A | vivo |
| R1-2200111 | Discussion on remaining issues for enhanced PUSCH repetition type A | ZTE |
| R1-2200160 | Enhancements on PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2200205 | Enhancements on PUSCH repetition type A | Samsung |
| R1-2200301 | Enhancements on PUSCH Repetition Type A | Qualcomm Incorporated |
| R1-2200334 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2200379 | Remaining details of enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2200420 | Discussion on PUSCH repetition type A enhancement | Apple |
| R1-2200500 | Enhancements on PUSCH repetition type A | Sharp |
| R1-2200518 | Type-A PUSCH repetition for coverage enhancement | InterDigital, Inc. |
| R1-2200588 | Remaining issues on PUSCH repetition type A enhancement | CMCC |
| R1-2200655 | Remaining Issues for PUSCH Repetition Type A Enhancement | Ericsson |
| R1-2200685 | FL Summary #1 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2200686 | FL Summary #2 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2200687 | FL Summary #3 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2200789 | FL Summary #4 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| 8.8.1.2 | TB processing over multi-slot PUSCH | |
| R1-2200052 | Discussion on TB processing over multi-slot PUSCH | Huawei, HiSilicon |
| R1-2200087 | Remaining issues on PUSCH TB processing over multiple slots | vivo |
| R1-2200112 | Discussion on remaining issues for TB processing over multi-slot PUSCH | ZTE |
| R1-2200152 | Remaining issues on TB processing over multi-slot PUSCH | CATT |
| R1-2200161 | Transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200206 | TB processing over multi-slot PUSCH | Samsung |
| R1-2200237 | TB processing over multi-slot PUSCH | NTT DOCOMO, INC. |
| R1-2200302 | TB processing over multi-slot PUSCH | Qualcomm Incorporated |
| R1-2200321 | Discussion on TB processing over multi-slot PUSCH | Panasonic Corporation |
| R1-2200335 | Further considerations for TB over multi-slot PUSCH | OPPO |
| R1-2200380 | Remaining details on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2200421 | Discussion on TB processing over multi-slot PUSCH | Apple |
| R1-2200466 | Discussion on TB processing over multi-slot PUSCH | xiaomi |
| R1-2200501 | TB processing over multi-slot PUSCH | Sharp |
| R1-2200509 | Discussion on remaining issue of TBoMS | NEC |
| R1-2200519 | TB processing over multiple slots | InterDigital, Inc. |
| R1-2200589 | Remaining issues on TB processing over multi-slot PUSCH | CMCC |
| R1-2200604 | Discussion on TBoMS PUSCH | TCL Communication Ltd. |
| R1-2200656 | Remaining Issues for TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2200680 | FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia) |
| R1-2200750 | FL summary #2 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2200751 | FL summary #3 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2200752 | Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| 8.8.1.3 | Joint channel estimation for PUSCH | |
| R1-2200053 | Discussion on joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2200088 | Remaining issues on joint channel estimation for PUSCH | vivo |
| R1-2200113 | Discussion on remaining issues for joint channel estimation for PUSCH | ZTE |
| R1-2200162 | Joint channel estimation for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200207 | Joint channel estimation for PUSCH | Samsung |
| R1-2200238 | Joint channel estimation for PUSCH | NTT DOCOMO, INC. |
| R1-2200268 | Discussion on joint channel estimation for PUSCH | Panasonic Corporation |
| R1-2200279 | Discussion on joint channel estimation for PUSCH | Spreadtrum Communications |
| R1-2200303 | Joint channel estimation for PUSCH | Qualcomm Incorporated |
| R1-2200336 | Consideration on Joint channel estimation for PUSCH | OPPO |
| R1-2200381 | Remaining details on joint channel estimation for PUSCH | Intel Corporation |
| R1-2200422 | Discussion on joint channel estimation for PUSCH | Apple |
| R1-2200467 | Discussion on joint channel estimation for PUSCH | xiaomi |
| R1-2200486 | Remaining issues on joint channel estimation | China Telecom |
| R1-2200487 | FL Summary of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2200499 | Joint channel estimation for PUSCH | Sharp |
| R1-2200520 | Discussions on joint channel estimation | InterDigital, Inc. |
| R1-2200553 | Discussion on Joint channel estimation over multi-slot | MediaTek Inc. |
| R1-2200590 | Remaining issues on joint channel estimation for PUSCH | CMCC |
| R1-2200613 | Discussions on joint channel estimation for PUSCH | LG Electronics |
| R1-2200657 | Remaining Issues for Joint Channel Estimation for PUSCH | Ericsson |
| R1-2200676 | Joint channel estimation for PUSCH | Samsung |
| R1-2200735 | FL Summary#2 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2200736 | FL Summary#3 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2200773 | LS on DMRS bundling for PUSCH and PUCCH | RAN1, China Telecom |
| R1-2200790 | [107-e-NR-R17-CovEnh-03] Summary of email discussion on joint channel estimation for PUSCH | Moderator (China Telecom) |
| 8.8.2 | PUCCH enhancements | |
| R1-2200054 | Discussion on PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2200089 | Remaining issues on PUCCH enhancements | vivo |
| R1-2200114 | Discussion on remaining issues for coverage enhancements for PUCCH | ZTE |
| R1-2200153 | Remaining issues on PUCCH enhancements | CATT |
| R1-2200163 | PUCCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200208 | PUCCH enhancements | Samsung |
| R1-2200239 | PUCCH enhancements for coverage enhancement | NTT DOCOMO, INC. |
| R1-2200280 | Discussion on PUCCH enhancements | Spreadtrum Communications |
| R1-2200304 | PUCCH enhancements | Qualcomm Incorporated |
| R1-2200322 | Discussion on the interaction between inter-slot frequency hopping and DMRS bundling | Panasonic Corporation |
| R1-2200337 | PUCCH enhancements for coverage | OPPO |
| R1-2200382 | Remaining details on PUCCH enhancements | Intel Corporation |
| R1-2200423 | Further discussion on PUCCH coverage enhancement | Apple |
| R1-2200468 | Discussion on PUCCH enhancements | xiaomi |
| R1-2200488 | Remaining issues on inter-slot frequency hopping with inter-slot bundling for PUCCH and PUSCH | China Telecom |
| R1-2200502 | PUCCH coverage enhancement | Sharp |
| R1-2200521 | Discussions on PUCCH enhancements | InterDigital, Inc. |
| R1-2200591 | Remaining issues on PUCCH enhancements | CMCC |
| R1-2200614 | Discussions on coverage enhancement for PUCCH | LG Electronics |
| R1-2200636 | Remaining issues on PUCCH enhancements for coverage enhancement | WILUS Inc. |
| R1-2200658 | Remaining Issues for PUCCH Dynamic Repetition and DMRS Bundling | Ericsson |
| R1-2200708 | FL summary #1 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2200754 | FL summary #2 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2200774 | FL summary #3 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2200806 | Final FL summary of PUCCH coverage enhancement | Moderator (Qualcomm) |
| 8.8.3 | Type A PUSCH repetitions for Msg3 | |
| R1-2200055 | Discussion on Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2200090 | Remaining issues on Type A PUSCH repetitions for Msg3 | vivo |
| R1-2200115 | Discussion on remaining issues for Type A PUSCH repetitions for Msg3 | ZTE |
| R1-2200154 | Remaining issues on Type A PUSCH repetitions for Msg3 | CATT |
| R1-2200164 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | Nokia, Nokia Shanghai Bell |
| R1-2200209 | Type A PUSCH repetitions for Msg3 | Samsung |
| R1-2200240 | Type A PUSCH repetitions for Msg3 | NTT DOCOMO, INC. |
| R1-2200305 | Type A PUSCH repetition for Msg3 | Qualcomm Incorporated |
| R1-2200323 | Discussion on Type A PUSCH repetitions for Msg.3 | Panasonic Corporation |
| R1-2200338 | Type A PUSCH repetitions for Msg3 coverage | OPPO |
| R1-2200383 | Remaining details on Msg3 PUSCH repetition | Intel Corporation |
| R1-2200424 | On remaining issues for Msg3 Coverage Enhancement | Apple |
| R1-2200469 | Discussion on Type A PUSCH repetition for Msg3 | xiaomi |
| R1-2200489 | Remaining issues on type A PUSCH repetitions for Msg3 | China Telecom |
| R1-2200503 | Type A PUSCH repetitions for Msg3 | Sharp |
| R1-2200522 | Type A PUSCH repetitions for Msg3 | InterDigital, Inc. |
| R1-2200592 | Remaining issues on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2200615 | Discussion on coverage enhancement for Msg3 PUSCH | LG Electronics |
| R1-2200637 | Remaining issues on Type A PUSCH repetitions for Msg3 | WILUS Inc. |
| R1-2200659 | Remaining Issues for Type A PUSCH Repetition for Msg3 | Ericsson |
| R1-2200712 | Feature lead summary #1 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2200713 | Feature lead summary #2 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2200714 | Feature lead summary #3 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2200802 | Feature lead summary #4 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| 8.8.4 | Other | |
| R1-2200116 | Discussion on RRC parameters for coverage enhancement | ZTE |
| R1-2200165 | Performance of Type A PUSCH repetitions for Msg3 for different MCS index configurations | Nokia, Nokia Shanghai Bell |
| R1-2200470 | Other considerations for coverage enhancement | xiaomi |
| R1-2200563 | Remaining issues on RRC parameters for NR coverage enhancement | vivo |
| R1-2200653 | Other considerations for coverage enhancement | Huawei, HiSilicon |
| R1-2200660 | Frequency Hopping for TBoMS | Ericsson |
| 8.11 | NR Sidelink enhancement | |
| R1-2200807 | [107bis-e-R17-RRC-Sidelink] Summary of email discussion on Rel-17 RRC parameters for sidelink enhancement | Moderator (LG Electronics) |
| R1-2200815 | Corrections further to the introduction of sidelink enhancements in NR | Samsung |
| R1-2200827 | Corrections further to the introduction of sidelink enhancements in NR | Nokia |
| R1-2200830 | Corrections on NR sidelink enhancement in 38.212 | Huawei |
| 8.11.1.1 | Resource allocation for power saving | |
| R1-2200015 | Resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2200021 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2200041 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2200091 | Remaining issues on resource allocation for sidelink power saving | vivo |
| R1-2200125 | Considerations on partial sensing and DRX in NR Sidelink | Fujitsu |
| R1-2200130 | Remaining issues on sidelink resource allocation enhancements for power saving | CATT, GOHIGH |
| R1-2200168 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2200181 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2200189 | Remaining issues on resource allocation for power saving | InterDigital, Inc. |
| R1-2200210 | On Resource Allocation for Power Saving | Samsung |
| R1-2200224 | Remaining Issues on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2200241 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2200281 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2200306 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2200347 | Remaining issues on power saving RA | OPPO |
| R1-2200359 | Discussion on resource allocation for power saving | ETRI |
| R1-2200384 | Remaining Details of Sidelink Resource Allocation Schemes for UE Power Saving | Intel Corporation |
| R1-2200425 | On Remaining Issues of Sidelink Resource Allocation for Power Saving | Apple |
| R1-2200436 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| R1-2200449 | Discussion on sidelink resource allocation enhancement for power saving | xiaomi |
| R1-2200474 | Sidelink resource allocation for power saving | Lenovo, Motorola Mobility |
| R1-2200505 | Discussion on resource allocation for power saving | Sharp |
| R1-2200510 | Discussion on resource allocation for power saving | NEC |
| R1-2200523 | Remaining issues on partial sensing and SL DRX impact | ASUSTeK |
| R1-2200545 | Resource allocation for sidelink power saving | MediaTek Inc. |
| R1-2200593 | Remaining issues on resource allocation for power saving | CMCC |
| R1-2200629 | NR Sidelink Resource Allocation for UE Power Saving | Fraunhofer HHI, Fraunhofer IIS |
| R1-2200638 | Remains on resource allocation for power saving in NR sidelink enhancement | ITL |
| R1-2200641 | Remaining aspects of resource allocation procedures for power saving | Ericsson |
| R1-2200720 | FL summary #1 for AI 8.11.1.1 – resource allocation for power saving | Moderator (OPPO) |
| R1-2200721 | FL summary #2 for AI 8.11.1.1 – resource allocation for power saving | Moderator (OPPO) |
| R1-2200722 | FL summary #3 for AI 8.11.1.1 – resource allocation for power saving | Moderator (OPPO) |
| R1-2200723 | FL summary #4 for AI 8.11.1.1 – resource allocation for power saving | Moderator (OPPO) |
| R1-2200724 | FL summary for AI 8.11.1.1 – resource allocation for power saving (EOM) | Moderator (OPPO) |
| R1-2200786 | FL summary #5 for AI 8.11.1.1 – resource allocation for power saving | Moderator (OPPO) |
| 8.11.1.2 | Inter-UE coordination for Mode 2 enhancements | |
| R1-2200016 | Inter-UE coordination for Mode 2 enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200022 | Discussion on techniques for inter-UE coordination | FUTUREWEI |
| R1-2200042 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2200092 | Remaining issues on mode-2 enhancements | vivo |
| R1-2200126 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2200131 | Remaining issues on Inter-UE coordination for Mode 2 enhancements | CATT, GOHIGH |
| R1-2200169 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2200170 | Feature lead summary #1 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2200171 | Feature lead summary #2 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2200172 | Feature lead summary #3 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2200182 | Discussion on inter-UE coordination for Mode 2 enhancements | Sony |
| R1-2200190 | Discussions on remaining issues for Mode 2 inter-UE coordination | InterDigital, Inc. |
| R1-2200211 | On Inter-UE Coordination for Mode2 Enhancements | Samsung |
| R1-2200225 | Inter-UE coordination for mode 2 enhancements | ITL |
| R1-2200242 | Resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2200270 | Considerations on mode2 enhancements | CAICT |
| R1-2200282 | Discussion on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2200307 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2200348 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2200360 | Discussion on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2200361 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2200385 | Inter-UE Coordination Solutions for Sidelink Communication | Intel Corporation |
| R1-2200426 | On Remaining Issues of Inter-UE Coordination | Apple |
| R1-2200437 | Remaining issues on the inter-UE coordination | ZTE, Sanechips |
| R1-2200450 | Discussion on inter-UE coordination | xiaomi |
| R1-2200475 | Inter-UE coordination for Mode 2 enhancements | Lenovo, Motorola Mobility |
| R1-2200504 | Discussion on inter-UE coordination for mode 2 enhancements | Sharp |
| R1-2200511 | Discussion on mode 2 enhancements | NEC |
| R1-2200524 | Remaining issues on V2X mode 2 enhancements | ASUSTeK |
| R1-2200554 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2200594 | Remaining issues on inter-UE coordination for mode 2 enhancement | CMCC |
| R1-2200630 | Inter-UE Coordination for Mode 2 Enhancements | Fraunhofer HHI, Fraunhofer IIS |
| R1-2200642 | Details on mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2200675 | Inter-UE coordination for Mode 2 enhancements | Panasonic |
| R1-2200745 | Feature lead summary #4 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2200746 | Feature lead summary #5 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2200747 | Feature lead summary #6 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2200748 | Feature lead summary #7 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2200749 | Feature lead summary #8 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| 8.11.2 | Other | |
| R1-2200093 | Other aspects on SL enhancements | vivo |
| R1-2200132 | Discussion on the status of Rel-17 Sidelink enhancements | CATT, GOHIGH |
| R1-2200191 | On gNB-designated resources for inter-UE coordination and sensing in SL DRX | InterDigital, Inc. |
| R1-2200212 | Discussion on Sidelink Enhancement | Samsung |
| R1-2200439 | Other enhancements on power saving | ZTE, Sanechips |
| R1-2200643 | Additional considerations on resource allocation regarding power saving and inter-UE coordination | Ericsson |
| R1-2200651 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| 8.12 | Maintenance on NR Multicast and Broadcast Services | |
| R1-2200795 | Session notes for 8.12 (NR Multicast and Broadcast Services) | Ad-Hoc Chair (Huawei) |
| R1-2200797 | Summary of email discussion on Rel-17 RRC parameters for NR MBS | Moderator (CMCC, Huawei, Qualcomm) |
| R1-2200810 | Agreements for NR MBS up to RAN1#107bis | Rapporteur (CMCC) |
| R1-2200814 | Corrections further to the introduction of multicast-broadcast services in NR | Samsung |
| R1-2200819 | Corrections to NR support of multicast and broadcast services | Ericsson |
| R1-2200822 | Corrections to NR support of multicast and broadcast services | Qualcomm Incorporated |
| R1-2200826 | Corrections further to the introduction of multicast-broadcast services in NR | Nokia |
| R1-2200832 | Corrections on NR Multicast and Broadcast Services in 38.212 | Huawei |
| 8.12.1 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | |
| R1-2200027 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2200094 | Remaining issues on mechanisms to support group scheduling for RRC_CONNECTED Ues | vivo |
| R1-2200117 | Discussion on Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2200133 | Remaining issues on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2200157 | Remaining Issues on Group Scheduling Mechanisms for RRC_CONNECTED Ues supporting MBS | Nokia, Nokia Shanghai Bell |
| R1-2200213 | Remaining issues on group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2200243 | Remaining issues on group scheduling mechanisms for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2200283 | Discussion on the remaining issues on MBS group scheduling for RRC_CONNETED UEs | Spreadtrum Communications |
| R1-2200308 | Maintenance on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2200350 | Discussion on remaining issues of group Scheduling mechanism for RRC_CONNECTED Ues | OPPO |
| R1-2200386 | Group Scheduling for RRC_CONNECTED Ues | Intel Corporation |
| R1-2200427 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Apple |
| R1-2200451 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | xiaomi |
| R1-2200471 | On group scheduling mechanism for RRC_CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2200512 | Remaining Issues on Group Scheduling Mechanisms for RRC_CONNECTED UEs | NEC |
| R1-2200525 | Further discussion on group scheduling for multicast mode | TD Tech, Chengdu TD Tech |
| R1-2200529 | Maintenance on mechanisms to support group scheduling for RRC_CONNECTED UEs | ETRI |
| R1-2200549 | Remaining issues on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2200578 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2200595 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2200596 | Remaining issues on group scheduling mechanisms for RRC_CONNECTED UEs | CMCC |
| R1-2200616 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ASUSTeK |
| R1-2200665 | Mechanisms to support MBS group scheduling for RRC_CONNECTED Ues | Ericsson |
| R1-2200670 | Corrections of MBS for RRC_CONNECTED UEs | Google Inc. |
| R1-2200681 | Remaining issues on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT, CBN |
| R1-2200731 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2200732 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2200733 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2200740 | FL summary#1 on MBS broadcast reception on SCell and non-serving cell | Moderator (Huawei) |
| R1-2200769 | FL summary#2 on MBS broadcast reception on SCell and non-serving cell | Moderator (Huawei) |
| R1-2200784 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2200785 | DRAFT LS reply to MBS broadcast reception on SCell and non-serving cell | Moderator (Huawei) |
| R1-2200798 | LS reply to MBS broadcast reception on SCell and non-serving cell | RAN1, Huawei |
| 8.12.2 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2200028 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2200095 | Remaining issues on mechanisms to improve reliability for RRC_CONNECTED Ues | vivo |
| R1-2200118 | Discussion on Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2200134 | Remaining issues on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2200158 | Remaining Issues on Reliability Improvements for RRC_CONNECTED UEs supporting MBS | Nokia, Nokia Shanghai Bell |
| R1-2200214 | Remaining issues on mechanisms to improve reliability | Samsung |
| R1-2200244 | Remaining details on HARQ-ACK feedback procedure for multicast | NTT DOCOMO, INC. |
| R1-2200284 | Discussion on the remaining issues on mechanisms to improve MBS reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2200309 | Maintenance on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2200351 | Remaining issues on UL feedback for MBS of RRC-CONNECTED UEs | OPPO |
| R1-2200387 | Reliability for RRC_CONNECTED UEs | Intel Corporation |
| R1-2200428 | Discussion on MBS reliability improvement for RRC_CONNECTED UEs | Apple |
| R1-2200472 | On reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2200513 | Remaining Issues on Reliability Improvements for RRC_CONNECTED UEs | NEC |
| R1-2200526 | PUCCH formats for enhancement to NACK-ONLY based HARQ-ACK feedback | TD Tech, Chengdu TD Tech |
| R1-2200550 | Remaining issues on improve multicast reliability for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2200579 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2200597 | Remaining issues on reliability improvement for RRC_CONNECTED UEs | CMCC |
| R1-2200666 | Discussion on reliability mechanisms for NR MBS | Ericsson |
| R1-2200682 | Remaining issues on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT, CBN |
| R1-2200717 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2200718 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2200719 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| 8.12.3 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | |
| R1-2200029 | Discussion on UE receiving broadcast in RRC IDLE/INACTIVE state | Huawei, HiSilicon, CBN |
| R1-2200096 | Remaining issues on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | vivo |
| R1-2200119 | Discussion on basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2200159 | Remaining Issues on Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE Ues | Nokia, Nokia Shanghai Bell |
| R1-2200215 | Remaining issues on broadcast/multicast for RRC_IDLE/RRC_INACTIVE Ues | Samsung |
| R1-2200245 | Remaining issues on basic functions for broadcast | NTT DOCOMO, INC. |
| R1-2200310 | Maintenance on group scheduling for Broadcast RRC_IDLE-INACTIVE UEs | Qualcomm Incorporated |
| R1-2200352 | Discussion on remaining issues of basic functions for RRC_IDLE/RRC_INACTIVE UEs | OPPO |
| R1-2200388 | Broadcast for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2200429 | Discussion on MBS for RRC_IDLE and RRC_INACTIVE UEs | Apple |
| R1-2200452 | Discussion on basic functions for broadcast/multicast for RRC_IDLERRC_INACTIVE UEs | xiaomi |
| R1-2200473 | Basic functions for broadcast/multicast in idle/inactive states | Lenovo, Motorola Mobility |
| R1-2200527 | Discussion on basic functions for broadcast mode | TD Tech, Chengdu TD Tech |
| R1-2200551 | Remaining issues on MBS broadcast reception for RRC_IDLE and INACTIVE UEs | MediaTek Inc. |
| R1-2200580 | Basic function for broadcast/multicast | LG Electronics |
| R1-2200598 | Remaining issues on NR MBS in RRC_IDLE RRC_INACTIVE states | CMCC |
| R1-2200667 | Support for NR broadcast reception in RRC Inactive/Idle | Ericsson |
| R1-2200705 | FL summary #1 on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Moderator (Qualcomm) |
| R1-2200706 | FL summary #2 on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Moderator (Qualcomm) |
| R1-2200707 | FL summary #3 on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Moderator (Qualcomm) |
| 8.12.4 | Other | |
| R1-2200097 | Other issues for Rel-17 MBS | vivo |
| R1-2200120 | Discussion on RRC parameters of Rel-17 MBS | ZTE |
| R1-2200135 | Discussion on other issues in Rel-17 MBS | CATT |
| R1-2200453 | Other remaining issues for MBS | xiaomi |
| R1-2200528 | Discussion on typical configuration for NR MBS | TD Tech, Chengdu TD Tech |
| R1-2200581 | Other aspects for MBS | LG Electronics |
| R1-2200617 | Discussion on further improvements for MBS | ASUSTeK |
| R1-2200646 | Views on overall configuration for broadcast scheduling | Huawei, HiSilicon |
| R1-2200668 | Assumptions for performance evaluations of NR-MBS | Ericsson |
| R1-2200683 | Discussion on other issues in Rel-17 MBS | CATT, CBN |
| 8.15 | Rel-17 UE Features | |
| R1-2200669 | On support of UE feature(s) for 32 HARQ processes in Rel-17 work items | Huawei, HiSilicon |
| R1-2200779 | Session Notes for 8.15 (Rel-17 UE Features) | Ad-Hoc Chair (NTT DOCOMO) |
| R1-2200780 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #107bis-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2200781 | LS on updated Rel-17 RAN1 UE features list for NR | RAN1, AT&T, NTT DOCOMO |
| 8.15.1 | UE features for further enhancements on NR-MIMO | |
| R1-2200031 | Rel-17 UE features for further NR MIMO enhancements | Huawei, HiSilicon |
| R1-2200057 | UE features for feMIMO | ZTE |
| R1-2200098 | Discussion on Rel-17 MIMO UE features | vivo |
| R1-2200136 | UE features for Rel-17 FeMIMO | CATT |
| R1-2200216 | UE features for further enhancements on NR-MIMO | Samsung |
| R1-2200246 | Discussion on Rel.17 FeMIMO UE features | NTT DOCOMO, INC. |
| R1-2200285 | Discussion on UE features for FeMIMO | Spreadtrum Communications |
| R1-2200311 | Discussion on FeMIMO UE features | Qualcomm Incorporated |
| R1-2200341 | UE features for further enhancements on NR-MIMO | OPPO |
| R1-2200389 | UE Features for FeMIMO | Intel Corporation |
| R1-2200430 | Views on Rel-17 FeMIMO UE features | Apple |
| R1-2200445 | MIMO Rel-17 UE features | FUTUREWEI |
| R1-2200454 | Discussion on UE features for FeMIMO | xiaomi |
| R1-2200493 | Discussion on Rel-17 UE feature for NR FeMIMO | LG Electronics |
| R1-2200535 | Discussion on UE features for FeMIMO | Lenovo, Motorola Mobility |
| R1-2200536 | Discussion on UE features for FeMIMO | Ericsson |
| R1-2200544 | UE Features for further enhancements on NR MIMO | MediaTek Inc. |
| R1-2200599 | Discussion on FeMIMO UE features | CMCC |
| R1-2200622 | On UE features for further enhancements on NR-MIMO | Nokia, Nokia Shanghai Bell |
| R1-2200734 | Proposal on UE Feature for Rel-17 Unified TCI | Samsung |
| R1-2200762 | Session Notes for Agenda Item 8.15.1 | Ad-Hoc Chair (AT&T) |
| R1-2200765 | Summary of UE features for further enhancements on NR-MIMO | Moderator (AT&T) |
| 8.15.2 | UE features for supporting NR from 52.6 GHz to 71 GHz | |
| R1-2200050 | Rel-17 UE features for extension to 71 GHz | Huawei, HiSilicon |
| R1-2200099 | Discussions on UE features for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2200217 | UE features for supporting NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2200247 | Views on Rel-17 UE features for supporting NR in FR2-2 | NTT DOCOMO, INC. |
| R1-2200266 | Discussion on UE features for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2200312 | UE features for NR from 52.6 Ghz to 71 Ghz | Qualcomm Incorporated |
| R1-2200330 | Discussion on UE feature for FR2-2 | OPPO |
| R1-2200390 | Discussion on UE capability for extending NR up to 71 GHz | Intel Corporation |
| R1-2200408 | UE features for extending current NR operation to 71 GHz | Ericsson |
| R1-2200431 | Views on Rel-17 Beyond 52.6 GHz UE features | Apple |
| R1-2200543 | Views on UE features for supporting NR from 52.6 GHz to 71 GHz | MediaTek Inc. |
| R1-2200582 | Discussion on UE features for NR above 52.6 GHz | LG Electronics |
| R1-2200623 | On UE features for supporting NR from 52.6 GHz to 71 GHz | Nokia, Nokia Shanghai Bell |
| R1-2200763 | Session Notes for Agenda Item 8.15.2 | Ad-Hoc Chair (AT&T) |
| R1-2200766 | Summary of UE features for supporting NR from 52.6 GHz to 71 GHz | Moderator (AT&T) |
| 8.15.3 | UE features for enhanced IIoT and and URLLC | |
| R1-2200014 | UE features for IIoT and URLLC | New H3C Technologies Co., Ltd. |
| R1-2200040 | Rel-17 UE features for enhanced IIoT/URLLC | Huawei, HiSilicon |
| R1-2200100 | Discussion on UE features for IIoT and URLLC | vivo |
| R1-2200121 | Discussion on UE features for enhanced IIoT and URLLC | ZTE |
| R1-2200138 | UE features for Rel-17 IIoT/URLLC | CATT |
| R1-2200218 | UE features for enhanced IIoT and URLLC | Samsung |
| R1-2200248 | Discussion on Rel.17 UE features for enhanced IIoT/URLLC | NTT DOCOMO, INC. |
| R1-2200249 | Summary on UE features for enhanced IIoT and and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2200286 | UE features for enhanced IIoT and and URLLC | Spreadtrum Communications |
| R1-2200313 | UE features for enhanced IIOT and URLLC | Qualcomm Incorporated |
| R1-2200346 | Discussion on UE features for IIoT and URLLC | OPPO |
| R1-2200391 | On UE features for enhanced IIoT and URLLC | Intel Corporation |
| R1-2200444 | Rel-17 UE Features for IIoT/URLLC | Ericsson |
| R1-2200557 | Views on UE features for enhanced IIoT and URLLC | MediaTek Inc. |
| R1-2200624 | On UE features for enhanced IIoT and and URLLC | Nokia, Nokia Shanghai Bell |
| 8.15.5 | UE features for NR positioning enhancements | |
| R1-2200036 | Rel-17 UE features for positioning enhancements | Huawei, HiSilicon |
| R1-2200058 | UE features for NR positioning enhancements | ZTE |
| R1-2200101 | Discussion on UE features for NR positioning enhancements | vivo |
| R1-2200139 | Remaining issues on Rel-17 UE features for NR Positioning enhancements | CATT |
| R1-2200219 | UE features for Pos enh | Samsung |
| R1-2200250 | Discussion on Rel-17 UE features for NR positioning enhancements | NTT DOCOMO, INC. |
| R1-2200271 | Discussion on UE Features for Positioning Enhancements | CAICT |
| R1-2200314 | UE features for NR positioning enhancements | Qualcomm Incorporated |
| R1-2200342 | UE features for NR positioning enhancements | OPPO |
| R1-2200457 | Discussion on UE features for NR Positioning Enhancements | xiaomi |
| R1-2200476 | UE features for NR positioning enhancements | Intel Corporation |
| R1-2200490 | UE features for Rel-17 NR positioning enhancements | China Telecom |
| R1-2200583 | UE features for Rel-17 positioning | MediaTek Inc. |
| R1-2200612 | Discussion on Rel-17 UE features for NR positioning | LG Electronics |
| R1-2200625 | On UE features for NR positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200663 | Views on NR positioning enhancements UE features | Ericsson |
| R1-2200764 | Session Notes for Agenda Item 8.15.5 | Ad-Hoc Chair (AT&T) |
| R1-2200767 | Summary of UE features for NR positioning enhancements | Moderator (AT&T) |
| 8.15.7 | UE features for UE power saving enhancements | |
| R1-2200035 | Rel-17 UE features for UE power saving enhancements | Huawei, HiSilicon |
| R1-2200071 | Discussion on UE feature for UE power saving enhancements | ZTE, Sanechips |
| R1-2200102 | Discussion on UE features for UE power saving enhancements | vivo |
| R1-2200140 | Discussion on UE feature of UE Power saving enhancements for NR | CATT |
| R1-2200220 | UE features for UE power saving enhancements | Samsung |
| R1-2200251 | Discussion on Rel-17 UE features for UE power saving | NTT DOCOMO, INC. |
| R1-2200252 | Summary on UE features for UE power saving enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2200315 | UE features for UE power saving enhancements | Qualcomm Incorporated |
| R1-2200339 | Rel-17 UE Power Saving features | OPPO |
| R1-2200392 | Discussion on UE features related to UE Power Saving | Intel Corporation |
| R1-2200432 | Views on UE features for Rel-17 UE power saving | Apple |
| R1-2200483 | UE features for UEPS | Ericsson |
| R1-2200538 | On UE features for UE power saving enhancements | MediaTek Inc. |
| R1-2200600 | Discussion on UE features for UE power saving enhancements | CMCC |
| R1-2200626 | On UE features for UE power saving enhancements | Nokia, Nokia Shanghai Bell |
| R1-2200678 | Summary on UE features for UE power saving enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2200741 | [Draft] LS on UE capability for paging enhancement | Ericsson |
| R1-2200742 | [Draft] LS on UE capability for paging enhancement | Ericsson |
| R1-2200768 | LS on UE capability for paging enhancement | RAN1, Ericsson |
| 8.15.8 | UE features for NR coverage enhancement | |
| R1-2200056 | Rel-17 UE features for NR coverage enhancement | Huawei, HiSilicon |
| R1-2200103 | Discussion on UE features for NR coverage enhancement | vivo |
| R1-2200122 | Discussion on UE features for NR coverage enhancement | ZTE |
| R1-2200141 | Discussion on Rel-17 UE features for NR coverage enhancement | CATT |
| R1-2200221 | UE features for NR coverage enhancement | Samsung |
| R1-2200253 | Discussion on Rel-17 UE features for NR coverage enhancement | NTT DOCOMO, INC. |
| R1-2200254 | Summary on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2200287 | UE features for NR coverage enhancement | Spreadtrum Communications |
| R1-2200316 | UE Features for Coverage Enhancements | Qualcomm Incorporated |
| R1-2200340 | Rel-17 Coverage Enhancement UE features | OPPO |
| R1-2200393 | Discussion on UE features for NR coverage enhancement | Intel Corporation |
| R1-2200433 | Views on Rel-17 Coverage enhancement UE features | Apple |
| R1-2200458 | UE features for NR coverage enhancement | xiaomi |
| R1-2200491 | UE features for Rel-17 NR coverage enhancements | China Telecom |
| R1-2200506 | UE feature for Rel-17 coverage enhancement | Sharp |
| R1-2200555 | Discussion on UE features for NR Coverage Enhancement | MediaTek Inc. |
| R1-2200601 | Discussion on Rel-17 UE features for NR coverage enhancement | CMCC |
| R1-2200627 | On UE features for NR coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2200661 | UE Features for NR Coverage Enhancement | Ericsson |
| 8.15.11 | UE features for NR sidelink enhancement | |
| R1-2200023 | UE features for NR sidelink enhancement | FUTUREWEI |
| R1-2200043 | Rel-17 UE features for NR sidelink enhancement | Huawei, HiSilicon |
| R1-2200104 | Discussion on UE features for NR sidelink enhancements | vivo |
| R1-2200137 | Discussion on Rel-17 UE features for sidelink enhancements | CATT, GOHIGH |
| R1-2200173 | Discussion on UE features for NR sidelink enhancement | LG Electronics |
| R1-2200222 | UE features for NR sidelink enhancement | Samsung |
| R1-2200255 | Discussion on Rel.17 UE features for NR SL enhancement | NTT DOCOMO, INC. |
| R1-2200256 | Summary on UE features for NR sidelink enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2200317 | UE Features for Sidelink Enhancements | Qualcomm Incorporated |
| R1-2200349 | On UE feature list for NR sidelink enhancement | OPPO |
| R1-2200434 | Views on Rel-17 NR Sidelink UE Features | Apple |
| R1-2200438 | Discussion on UE features for NR sidelink enhancement | ZTE, Sanechips |
| R1-2200455 | Discussion on Rel-17 UE features on sidelink enhancement | xiaomi |
| R1-2200477 | UE features for NR sidelink enhancement | Intel Corporation |
| R1-2200546 | UE features for NR sidelink enhancements | MediaTek Inc. |
| R1-2200602 | Discussion on UE features for NR sidelink enhancement | CMCC |
| R1-2200644 | UE features for NR sidelink enhancements | Ericsson |
| 8.15.12 | UE features for NR MBS | |
| R1-2200030 | Rel-17 UE features for NR MBS | Huawei, HiSilicon |
| R1-2200105 | Discussion on UE features for MBS | vivo |
| R1-2200123 | Discussion on Rel-17 UE features for NR MBS | ZTE |
| R1-2200223 | UE features for NR MBS | Samsung |
| R1-2200257 | Discussion on Rel.17 UE features for NR MBS | NTT DOCOMO, INC. |
| R1-2200258 | Summary on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2200288 | UE features for MBS | Spreadtrum Communications |
| R1-2200318 | UE features for MBS | Qualcomm Incorporated |
| R1-2200354 | Discussion on UE feature for NR MBS | OPPO |
| R1-2200394 | UE Features for NR MBS | Intel Corporation |
| R1-2200435 | Views on Rel-17 MBS UE features | Apple |
| R1-2200456 | Discussion on UE features for NR MBS | xiaomi |
| R1-2200552 | Views on UE features for NR MBS | MediaTek Inc. |
| R1-2200603 | Discussion on UE features for NR MBS | CMCC |
| R1-2200628 | On UE features for NR MBS | Nokia, Nokia Shanghai Bell |
| R1-2200664 | views on NR MBS UE features | Ericsson |